Techniques for guaranteeing bandwidth with aggregate traffic

ABSTRACT

Methods, systems, and apparatus guarantee bandwidth for a network transaction. A network is logically organized as a tree having a plurality of nodes. Each node can guarantee service for a network transaction through the network. Each node monitors its traffic and reserves predefined amounts of unused bandwidth with its adjacent node. If a particular node needs additional bandwidth, that node borrows the bandwidth from its adjacent node.

This application is a continuation of U.S. patent application Ser. No.14/153,846, filed Jan. 13, 2014, which is a continuation of U.S. patentapplication Ser. No. 11/383,980, filed on May 18, 2006, now issued asU.S. Pat. No. 8,631,151, which is a continuation under 35 U.S.C. 111(a)of International Application No. PCT/CN2003/001141, filed on Dec. 30,2003, and published in English on Jul. 21, 2005 as InternationalPublication No. WO 2005/067203 A1, all of which are incorporated hereinby reference in their entireties.

TECHNICAL FIELD

Embodiments of the present invention relate generally to computernetworks, and more particularly to bandwidth management for networktraffic.

BACKGROUND INFORMATION

Quality of Service (QoS) is the concept that transmission rates, errorrates, and other network transmission characteristics can be measured,improved, and to some extent guaranteed in advance of a networktransmission. QoS is a significant concern for high bandwidth networksthat regularly transmit large amounts of data such as video, audio,multimedia, and the like. Moreover, QoS is problematic forgeographically dispersed networks, such as the Internet, where anysingle network transaction can span multiple sub-networks throughmultiple Internet Service Providers (ISPs).

Attempts to provide decent QoS architectures often suffer fromscalability issues. That is, independent sub-networks (e.g., ISPs) arerequired to be too heavily dependent upon one another to produce anyviable commercial solution. As soon as independent sub-networks becomedependent upon the operational specifics of other sub-networks, theybecome less scalable and less desirable. When scalability is adequatelyachieved, the result is usually achieved with overly compleximplementation schemes that dramatically decrease network throughput atthe expense of providing scalability.

Accordingly a more scalable QoS technique for large geographicallydisperse networks is needed, where scalability is achieved in a mannerthat does not significantly impact network throughput and is not overlycomplex.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is diagram of a network to guarantee service in accordance withone embodiment of the invention.

FIG. 2 is a flow diagram of a method to guarantee network service inaccordance with one embodiment of the invention.

FIG. 3 is a flow diagram of a method to manage bandwidth of a guaranteednetwork service request in accordance with one embodiment of theinvention.

FIG. 4 is a diagram of a bandwidth management system in accordance withone embodiment of the invention.

DESCRIPTION OF THE EMBODIMENTS

FIG. 1 is a diagram of a network 100 that guarantees service for networktransactions before the transactions are processed within the network100. The technique is implemented in a computer-accessible medium withinprocessing devices of a network. These devices can be routers, hubs,bridges, switches, gateways, firewalls, proxies, servers, clientworkstations, and the like. The network 100 is logically represented inthe computer-accessible medium as a tree where each branch of the treeis a node. A node is a processing device that participates in a networktransaction by routing data packets associated with the networktransaction between originating nodes and destination nodes.

The embodiments of this invention provide improved techniques forguaranteeing service between node of a network 100. Guaranteeing meansthat bandwidth availability is assured before a network transactioncommences, assuming that the nodes and links of the network 100 remainoperational and do not otherwise fail. One of ordinary skill in the artreadily appreciates that an absolute assurance that a networktransaction will complete within a network 100 is not feasible, sincelinks and nodes can fail abnormally due to hardware or softwarefailures, or links and nodes can fail due to planned maintenanceactivity.

The network 100 depicted in FIG. 1 includes a variety of AutonomousSystems (AS) that can operate independently of one another. These ASscan be viewed as independent sub-networks, such as ISPs, privatenetworks and the like. The sub-networks can geographically span theentire world. Within each AS, a number of processing nodes are used todirectly communicate with other external ASs; these nodes are referredto as edge nodes.

The entire network 100 is logically organized as a tree. In FIG. 1, thattree is inverted, such that the root of the tree is identified by AS Yand the farthest leaf is identified by AS X. The root node of the treeis edge node ID. AS N is a father of children 0, 1, and 2. Moreover, thechildren are considered brothers to each other. Each AS can itself beconsidered a sub-tree, having its own internal root node, father node,and brother nodes. Moreover, the children of a father are considered itssons. Thus, father AS N has sons identified as Child 0, Child 1, andChild 2. Moreover, AS N is considered a grandfather of AS X.

A network transaction is a communication between any two or more nodesof the network 100. A node that originates the network transaction iscalled an originating node. A network transaction transfers data packetsfrom an originating node to a destination node. Thus, the node that theoriginating node desires to communicate with via a network transactionis referred to as a destination node. A network transaction will includethe transfer of one or more network data packets from the originatingnode through one or more intermediate nodes to the destination node.Thus, the network transaction is associated with a path through thenetwork from the originating node to the destination node. A variety ofpath generating and dynamic modifying algorithms are well known in thenetworking arts and readily achievable using existing networkarchitectures and protocols. All such algorithms and architectures arecapable of being used with the embodiments of this invention.

The volume of and rate at which network packets are present and sentbetween any two nodes of the network 100, is referred to as thebandwidth. These data transfers occur over the links of the network 100,the links connect the nodes. Each link can be capable of handlingdifferent types of media, different volumes, different rates, and adifferent number of concurrent sessions of network transactions. Thehard and soft limitations of each link are known in advance by each nodebased on its hardware and software configurations. These limitations canbe communicated between nodes using well known and existing networkingprotocols and technologies.

When an originating node requests a particular network transactiondirected to a destination node, the originating node would like to knowin advance of commencing the transaction that a sufficient amount ofbandwidth will exist within the network 100 in order to process thetransaction to the destination node. In embodiments of the presentinvention, this is achieved with a Bandwidth Conservation Criterion(BCC) calculation. The originating node makes a request for a networktransaction to the first processing node defined in the network path.The first processing node identifies the total available bandwidth ofthe destination node and sums the bandwidth of all outstanding trafficthat is destined for the destination node. This calculation is the BCCcalculation that guarantees the originating node that bandwidth willexist to satisfy the transaction. IN response to the guarantee, theoriginating node commences the network transaction through the network100.

As an example, consider an originating node A that requests a networktransaction requiring 10 KB of bandwidth. The transaction is directed todestination node N and is initially requested of initial processing nodeB. N can have a maximum bandwidth of 128 KB. When A makes the request toB, the current aggregate traffic directed to N is 110 KB.

In the present example, B applies BCC to determine that if the networktransaction is guaranteed there will be 120 KB of current trafficdirected towards N, which is less than the maximum bandwidth of 128 KBthat N can handle at any point in time. Thus, B makes the BCCcalculation when it receives the request from A and determines that thenetwork transaction can be guaranteed. The guarantee is thencommunicated from B to A, and the network transaction commences.

BCC can be defined with the following equations, where the originatingnode is the node identified in AS X and the destination node is edgenode D of AS Y (the root of the tree):

$\quad\{ \begin{matrix}{{\sum\limits_{i}\; r_{ij}^{D}} \leq r_{jk}^{D}} \\{B_{ij}^{X} = {\sum\limits_{y}\; r_{ij}^{y}}}\end{matrix} $B_(ij) ^(X) is the overall bandwidth of AS X available between edgenodes i and j and r_(ij) ^(D), the corresponding portion of AS X in thetree rooted by edge node D. Thus, if the bandwidth request associatedwith a network transaction when combined with the total aggregatebandwidth destined for edge node D is less than the total bandwidth thatedge node D can handle, the BCC equation holds true and a networktransaction can be guaranteed service.

This calculation is a scalable approach, because all that is needed is acalculation that sums existing aggregate traffic that is being directedto a destination node along with the known bandwidth limit associatedwith the destination node. By aggregate traffic it is meant that allcurrent network traffic that is active in the network and is currentlybeing directed to the destination node. However, at any given point asthe network transaction is progressing through the network 100, one ormore nodes may not have sufficient bandwidth to handle the networkrequest. Thus, BCC can be augmented to make necessary dynamicadjustments as needed at each processing node associated with a networkpath of a network transaction, which is guaranteed by the BCC equation.

For example, a network transaction may progress after a guarantee ofservice from AS m to edge node j′ of AS Y. At this point in time,however, the current bandwidth for the link between node j′ and k (linkj′-k) may be at capacity and not capable of handling the networktransaction. Without the ability for link j′-k to increase its bandwidththe transaction may fail or become unreasonably delayed. Thus, thestatic approach of BCC can be augmented with a Closest relationAllocatioN (CLAN) technique, that permits nodes to borrow bandwidth fromadjacent (brother, son, father) nodes.

With the CLAN technique, each node of the network 100 monitors thetraffic volume occurring with its link to its adjacent nodes, morespecifically with its father node. When a particular node notices areduction in bandwidth occurring with its link to its father node, thatreduction is known to the father node (adjacent node). This reservedbandwidth is held by the father node and delivered to other more needingsons of the father when needed.

Thus, in the example, presented above, if the link j′-k can hold 128 KBvolume and is at capacity when a network transaction comes along thatneeds to reach node k, then node k can borrow 64 KB from one or both ofits two remaining sons. Node k knows the 64 KB is obtainable from one orits two remaining sons, because if finds the two remaining sons havingchunks of available bandwidth to their father node K during processingand request bandwidth from their father node when needed.

For example, consider that the three links to node k each have a totalbandwidth capacity of 128 KB and consider further that each son node isconfigured to manage only 64 KB of capacity at any one time andconfigured to release and to notify the father node k whenever bandwidthis needed above 64 KB and the father node will be aware when capacityabove 64 KB is no longer needed for any given transaction. The fathernode k then manages this excess bandwidth and when a network transactionmoving from link j′-k, in our present example, needs additionalbandwidth; the father node k has it in reserve to deliver to the sonnode j′, because the bandwidth has been previously borrowed from one orboth brothers of node j′.

Borrowing can occur between any two adjacent nodes or brother nodes.Moreover, the borrowing need not occur within a single AS. For exampleedge node j′ connects two different ASs (L and M) to AS N. Thus, edgenode j of AS M can borrow from the appropriate edge node of AS L inorder to complete a transaction over link j-j′. This occurs through j′,which acts as an adjacent node or father node to both node j and theedge node of AS L that directly connects to node j′.

Thus, with CLAN, adjacent nodes establish policies with one another suchthat chunks of bandwidth are managed by father nodes on behalf of theirsons. These chunks of bandwidth are considered reserves, which must berequested before the reserves can be used from the appropriate fathernode. Thus, son nodes borrow, via their father, bandwidth that exceeds apre-negotiated amount; the bandwidth borrowed comes from the brothernodes of a borrowing son node, but is managed by their father node. In asimilar fashion father node can borrow from its father within thenetwork 100, such that at any one time a borrowing node may be gettingbandwidth from its brothers and from brothers of its father.

Hierarchical relationships between nodes of a network are managed inorder to borrow bandwidth with the CLAN technique; the borrowing isneeded for a network transaction that is progressing through nodes of anetwork. That is, a node in need of more bandwidth uses its closestrelationship to adjacent nodes to acquire the necessary bandwidthallocation and this borrowing can progress upward through that node'srelatives after first borrowing from its closest relation.

Further, the BCC calculation permits a transaction guarantee to be givento an originating node of a network transaction, where that networktransaction requires a certain amount of bandwidth through a network 100in order to reach a destination node. Moreover, as the networktransaction progresses through the network 100, if any particular linkbetween nodes lacks sufficient bandwidth to process the transaction, thebandwidth can be temporarily borrowed from adjacent nodes using the CLANtechnique. The BCC and CLAN techniques provide a scalable solution toQoS for ASs or independent networks. These techniques are not overlycomplex and can be implemented within existing network protocols andsoftware designed to calculate the BCC and implement the CLAN technique.

FIG. 2 is a flow diagram of one method 200 to guarantee network serviceby implementing the BCC and CLAN techniques discussed above with FIG. 1.The method 200 is implemented in a computer accessible medium andprocesses on each node of a network. The nodes are processing devices inthe network which originate, route, and process network transactionsthrough a network. The method 200 can be implemented within each node ofthe network as software, firmware, and/or via network protocols.

Initially, at 210, a request for a network transaction is received by afirst processing node. The request originates from an originating node.The network transaction is associated with a network path which definesone or more routes for network packets associated with the networktransaction to traverse through one or more intermediate nodes of thenetwork to a destination node. The first processing node is the firstnode of that network path.

When the first processing node receives the network request from theoriginating node, it determines whether the request is acceptable basedon the BCC calculation by checking if the aggregate traffic existing inthe network which is destined for the destination node plus thebandwidth needed by the network transaction exceeds the destinationnode's maximum bandwidth. The BCC calculation and the appropriate checkare made at 220. If the aggregate traffic plus the bandwidth needed doesexceed the destination node's bandwidth limit, then, at 222, the networktransaction cannot be guaranteed and the originating node is notified ofthe same.

However, if at 220, the aggregate traffic plus the bandwidth needed doesnot exceed the destination node's bandwidth limit, then, at 230, thefirst processing node guarantees to the originating node that therequested network transaction will have sufficient bandwidth to reachthe destination node within the network. In one embodiment, as soon asthis guarantee occurs, the total available bandwidth at the destinationnode is decremented at 240 by the bandwidth which is needed to satisfythe current network transaction.

Of course there are a variety of ways to implement the BCC calculation.One technique would be to have the destination node keep track oftraffic headed its way and maintain a current available bandwidthcounter, which is constantly and dynamically changing. Another way is tohave each node dynamically make queries to other nodes in the network todynamically calculate the BCC. One skilled in the art will readilyappreciate that other techniques can also exist. All such techniques,which resolve the BCC calculation, are intended to be included in theembodiments of this invention.

Once the first processing node guarantees service, the networktransaction commences to process through the network to the destinationnode at 250. In some embodiments, at some point, during the processingof the network transaction, a particular processing node may determinethat it actually lacks the necessary bandwidth needed to process thenetwork transaction through a link to a next node of the network pathassociated with the network transaction, as depicted at 260. Each nodeof the network dynamically implements the CLAN technique discussed abovewith FIG. 1 in order to dynamically resolve this problem.

Accordingly, at 270, the particular processing node that lackssufficient bandwidth borrows the needed bandwidth from an adjacent nodein order to process the network transaction. Thus, the father node ofthe particular processing node manages reserve bandwidth on behalf ofthe particular processing node and the particular processing node'sbrother nodes. These nodes pre-establish with one another the amount ofexcess bandwidth that the father node will be responsible for managingand delivering, if and when excess bandwidth is needed by any of thesons of the father. Additionally, in some embodiments, the father nodeof a needy son may not have sufficient bandwidth to satisfy a needingson's bandwidth request. In these situations, the father contacts hisfather (adjacent node to the father and grandfather of the needing son)in order to borrow bandwidth from brothers of the father (grandfather tothe needing son). This borrowing continues as needed according to therules associated with the CLAN technique, as described above in FIG. 1.

The embodiments of method 200 demonstrate how the BCC and CLAN techniquecan be implemented and processed within nodes of a network in order toprovide a scalable QoS from heterogeneous ASs logically organized as asingle network. These embodiments are not complex and can be deployedwith software processing on each network node that uses conventionalnetwork protocols to communicate between nodes.

FIG. 3 is a flow diagram of one method 300 to manage bandwidth of aguaranteed network service request. The method 300 is implemented withineach node of a network and is implemented in a computer accessiblemedium. The method 300 represents processing performed by each node andsome interactions occurring between nodes during a network transaction.The method 300 represents embodiments of the CLAN technique, where nodesborrow and manage bandwidth within a network during a networktransaction.

At 310, a processing node associated with processing a networktransaction through a network to a destination node monitors its owntraffic volume. The processing node has previously used policies knownto its adjacent nodes (brothers, father, and sons) in order to configureit to monitor traffic at specific predefined levels. When traffic fallsbelow the predefined limit, then this is detected at 320, and predefinedamounts of bandwidth that are available are reserved as beingunavailable to the processing node at 330.

Those predefined amounts of reserved bandwidth are known to theprocessing node's father node (adjacent node) at 340. The father nodemanages a pool of reserved bandwidth on behalf of the processing nodeand on behalf of brothers of the processing node. Thus, at 350, whenanother node (brother node of the original processing node) isprocessing its own network transaction and determines that it needsadditional bandwidth to process the network transaction through to thefather node, the brother node makes a request at 360 to borrow theneeded bandwidth from the father node (adjacent node). The brother hasdirectly borrowed the bandwidth from the father, but indirectly borrowedit from the excess capacity that the brother's siblings had previouslydeposited with the father for purposes of management.

This bandwidth management and borrowing technique reflects an exampleimplementation of the CLAN technique discussed above with FIGS. 1 and 2.Policies about management associated with bandwidth deposits (e.g.,reservations) and withdrawals are communicated between adjacent nodes ofthe network. Moreover, at 370, each node of the network is capable ofresolving the BCC calculation when needed by maintaining techniques forresolving (e.g., calculating) the aggregate bandwidth associated withany particular destination node of a particular network transaction.

Method 300 provides an example implementation of the CLAN technique andmaintains the capabilities when needed to perform the BCC calculation.This demonstrates how a heterogeneous network consisting of a pluralityof nodes can interact in a scalable fashion with one another to provideQoS for a network transaction.

FIG. 4 is a diagram of one bandwidth management system 400. Thebandwidth management system 400 represent an embodiment of the BCC andCLAN technique within a heterogeneous network, where the networkincludes a plurality of sub-networks identified as ASs. The bandwidthmanagement system 400 is implemented in a computer accessible medium.

The bandwidth management system 400 includes logically representing theheterogeneous network as a network tree 401, wherein branches of thetree 401 can include other sub-trees. The tree 401 can be entirelymanaged and manipulated by pointers and metadata associated with theattributes and characteristics of the tree 401. The tree 401 includes aplurality of nodes 402 and 403. Each node 402 or 403 assumes adesignation as a son, father, and/or brother depending upon its contextwithin the tree to another adjacent node 402 or 403. Thus, a single node402 or 403 can have multiple designations with respect to adjacent nodes402 and 403. A node can also have a designation with respect tonon-adjacent nodes, such as grandfather, grandson, uncle, and the like.

Each node 402 or 403 also includes its own traffic monitor 402A-403A,bandwidth modifier 402B-403B, and signaling processor 402C-403C. Theseentities combine both software logic and existing networking protocolsto perform the BCC and CLAN techniques.

Thus, the traffic monitor 402A-403A monitors traffic on its respectivenode 402 or 403 and communicates traffic information to the trafficmonitors 402A-403A of its adjacent nodes 402 or 403. This communicationand monitoring is useful in resolving the processing associated with theBCC and CLAN techniques. For example, traffic volumes can be aggregatedto resolve the BCC calculation for a particular destination node of aparticular network transaction. Moreover, the traffic volumes can beused to determine whether to deposit bandwidth with or to withdraw onloan bandwidth from an adjacent node 402 or 403.

The bandwidth modifier 402B-403B communicates with the traffic monitor402A-403A in order to adjust bandwidth associated with its particularprocessing node 402 or 403. That is, when the traffic monitor 402A-403Areports bandwidth below a predefined and pre-negotiated amount, thebandwidth modifier 402B-403B can be used to implement the CLAN techniqueand claim additional bandwidth not being used as reserved bandwidth,which is then deposited with an adjacent node 402 or 403. Conversely,when a node 402 or 403 needs additional bandwidth, the bandwidthmodifier 402B-403B can be used to detect this need based on a currenttransaction and based on reports of bandwidth usage from the trafficmonitor 402A-403A in order to request more bandwidth on loan from anadjacent node 402 or 403.

The signaling processor 402C-403C can be used to actually allocate andreallocate need bandwidth or excess bandwidth from an adjacent node 402or 403. That is, the actual device that permits bandwidth to beredirected to a specified link can be controlled with the signalingprocessor 402C-403C. In essence, bandwidth is reallocated and throttledup or throttled down over physical links when bandwidth is deposited orwithdrawn from an adjacent node 402 or 403. This throttling is theresponsibility of the signaling processor 402C-403C.

During operation, the traffic monitor 402A-403A reports traffic on itsnode 402 or 403 to the adjacent nodes 402 or 403. The bandwidth modifier402B-403B uses this in combination with existing network requests tomodify bandwidth. The signaling processor 402C-403C detects modifiedbandwidth and drives the underlying bandwidth device to throttle up anddown affected links of the nodes 402 and 403.

The use of the traffic monitor 402A-403A, the bandwidth modifier402B-403B, and the signaling processor 402C-403C provides a modularevent-driven implementation of the BCC and CLAN technique that isscalable across a large heterogeneous network. However, one of ordinaryskill in the art appreciates that other implementations andarchitectures are possible where the functions of the modules arefurther isolated into more modules or combined into less modules. Allsuch modifications to this architecture that are designed to perform theBCC or CLAN techniques fall within the scope of the embodiments for thisinvention.

The above description is illustrative, and not restrictive. Many otherembodiments will be apparent to those of skill in the art upon reviewingthe above description. The scope of embodiments of the invention shouldtherefore be determined with reference to the appended claims, alongwith the full scope of equivalents to which such claims are entitled.

The Abstract is provided to comply with 37 C.F.R. § 1.72(b) requiring anAbstract that will allow the reader to quickly ascertain the nature andgist of the technical disclosure. It is submitted with the understandingthat it will not be used to interpret or limit the scope or meaning ofthe claims.

In the foregoing description of the embodiments, various features aregrouped together in a single embodiment for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments of the inventionrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, inventive subject mater lies in lessthan all features of a single disclosed embodiment. Thus the followingclaims are hereby incorporated into the Description of the Embodiments,with each claim standing on its own as a separate exemplary embodiment.

What is claimed is:
 1. A non-transitory computer-readable mediumincluding executable instructions that when executed by a network deviceperforms a method to: receive a network transaction request from apreceding network device to the network device requesting that a networktransaction be processed through the network device to a next networkdevice; reserve an amount bandwidth from at least one adjacent networkdevice that has a network link with preceding network device to ensurethe amount of bandwidth when processing the network transaction throughthe network device to the next network device and make dynamicadjustments for the amount of bandwidth as the network transactiondynamically progresses through a network; and processing, over thenetwork, the preceding network device, the network device, the at leastone adjacent device, and the next network device as independent andautonomous devices from one another for the network transaction.
 2. Themedium of claim 1 further comprising instructions to request that thenext network device set aside the amount of bandwidth for processing thenetwork transaction in advance of processing the network transaction. 3.The medium of claim 2, wherein the instructions to reserve amount ofbandwidth further includes instructions to request that the next networkdevice instruct a further network device to the next network device thatis along a path for the network transaction to reserve the amount ofbandwidth with that further network device in advance of processing thenetwork transaction.
 4. The medium of claim 1, wherein the instructionsto reserve the amount of bandwidth further includes instructions toreserve the amount of bandwidth from more than one adjacent networkdevice.
 5. The medium of claim 1, wherein the instructions to reservethe amount of bandwidth further includes instructions to determine anexisting amount of bandwidth in use by the network device when withnetwork transaction is received to determine the amount of bandwidth andidentify the at least one adjacent network device.
 6. The medium ofclaim 1, wherein the preceding network device, the network device, thenext network device, and the at least one adjacent network device arenetwork routers.
 7. The medium of claim 1, wherein the instruction toreceive further include to identify in the network transaction request apath for processing the network transaction through a network from anoriginating network device to a destination network device.
 8. Themedium of claim 7, wherein the instructions to identify further includesinstructions to identify the next network device from the path.
 9. Themedium of claim 1, wherein the instruction to receive further includeinstructions to aggregate pending network bandwidth for identifyingexisting bandwidth in use by the network device and the at least oneadjacent network device when the network transaction request isreceived.
 10. A network device, comprising: a processor; and a memory;wherein the processor is configured to process executable instructionsresiding in the memory and when the executable instructions areprocessed cause the processor to: reserve excess bandwidth to processthe network transaction from at least one adjacent network device to thenetwork device, make dynamic adjustments for the excess bandwidth as thenetwork transaction progresses through a network, and process thenetwork device over the network autonomously and independently of the atleast one adjacent network device for the network transaction.
 11. Thenetwork device of claim 10, wherein when the executable instructions areprocessed the processor further caused to aggregate existing networkbandwidth in use by the network device and the at least one adjacentnetwork device to determine available bandwidth to the network deviceand the at least one adjacent network device.
 12. The network device ofclaim 10, wherein when the executable instructions are processed theprocessor further caused to instruct a next network device for thenetwork transaction to reserve an amount of bandwidth to process thenetwork transaction.
 13. The network device of claim 10, wherein whenthe executable instructions are processed the processor further causedto identify an amount of bandwidth to process the network transaction inresponse to a network transaction request received from a precedingnetwork device to the network device.
 14. The network device of claim12, wherein when the executable instructions are processed the processorfurther caused to determine the excess bandwidth as a difference betweenavailable bandwidth for the network device and the at least one adjacentnetwork device when the network transaction request is received at thenetwork device subtracted from the amount of bandwidth.
 15. The networkdevice of claim 14, wherein the network device connected through networklinks to the preceding network device, the at least one adjacent networkdevice, and a next network device that is to process the networktransaction.
 16. The network device of claim 10, wherein network deviceis one of: a router, a hub, a bridge, a switch, a gateway, a firewall, aproxy, and a server.
 17. A system, comprising: a plurality of networkdevices connected through network links; wherein each network deviceconfigured to: guarantee an amount of bandwidth for processing a networktransaction through the network links in advance of processing thenetwork transaction, borrow at least some of the amount of bandwidthfrom an adjacent network device to that network device, make dynamicadjustments for the amount of bandwidth as the network transactionprogresses through a network, and process over the network each networkdevice autonomously and independently of remaining ones of the networkdevices for the network transaction.
 18. The system of claim 17, whereineach network device is further configured to: aggregate existingbandwidth available to that network device and that network device'sadjacent network device to determine a borrow amount of bandwidth torequest from that adjacent network device.
 19. The system of claim 17,wherein each network device is further configured to identify a nextnetwork device from the plurality of network devices from a path of thenetwork transaction.
 20. The system of claim 19, wherein the pluralityof network devices are one or more of: a router, a hub, a bridge, aswitch, a gateway, a firewall, a proxy, a server, and a clientworkstation.